[plugin] [ORPHAN] zem_event [flexible integrated event management]

zem · 2007-02-02 01:41:22

Just for fun, here’s what sloccount says about zem_event:

Total Physical Source Lines of Code (SLOC)                = 1,466
Development Effort Estimate, Person-Years (Person-Months) = 0.30 (3.59)
 (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months)                         = 0.34 (4.06)
 (Basic COCOMO model, Months = 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule)  = 0.88
Total Estimated Cost to Develop                           = $ 40,372
 (average salary = $56,286/year, overhead = 2.40).
SLOCCount, Copyright (C) 2001-2004 David A. Wheeler
SLOCCount is Open Source Software/Free Software, licensed under the GNU GPL.

Based on those figures, a bottom rung $16/hr PHP outsourcing firm would have charged over $9000 for the work done sofar. Never mind the difference in quality.

Of course that doesn’t take into account the efficiency and quality you get from modern agile software development processes, or from open source. Which is precisely why we were able to build it at such a low cost.

renobird · 2007-02-02 04:19:32

Matthew,

Thanks for the response. Looks like the 2nd one of the day that’ll cost me. : )
However, both will be well worth the cost. I’ll need a few more days to test the plug-in, and then I’ll get a formal list of requests together. Looks pretty amazing right out of the box though.

Cheers,
Tom

Last edited by renobird (2007-02-02 04:20:08)

squaredeye · 2007-02-02 15:13:06

Tom,
That’s a great way to approach it. If you’d like you can email me directly and I’ll get a request list started at the top of the list, and find out how much funding we can get behind it :)

jstubbs · 2007-02-02 18:51:19

ma_smith wrote:

It would make sense if that were included with the price of this plugin, but it was not, if we would like to pay for more, that can be arranged. For styling, you can see what I have on the provided links, and I am happy to try to work with folks, but we are in the same boat :) PHP development does not come cheap, and we have all benefitted from folks who have a sense of philanthropy or hobby about provididing plugins, but for folks like the TeamTextpattern crew, they need to make a living :)

Fair enough. Of course they need to charge whatever they see fit to charge, and yes, we all benefit from plugins and the open source solutions. It just seems odd that if one were to pay a lot of money for a plugin no instructions are available on how to use the plugin.

None of our business really, except for the fact that it has been released to the public after a ransom.

zem wrote:

Of course that doesn’t take into account the efficiency and quality you get from modern agile software development processes, or from open source. Which is precisely why we were able to build it at such a low cost.

OK. Hope you keep creating new plugins and expanding on the fantastic TXP. Great work from the developers.

zem · 2007-02-02 22:48:54

It just seems odd that if one were to pay a lot of money for a plugin no instructions are available on how to use the plugin.

Just for the record, we did provide Matthew with instructions and examples. Our part of the job was delivering software to his specifications and requirements. The ransom and public release is Matthew’s baby.

This is kind of a new thing for all of us. I hope we can keep doing it too.

Enough said I think.

RenJonsin · 2007-02-03 02:12:02

jstubbs wrote:

Is it the case that you don’t have a full list of the tags available and the style elements that we can use with each tag? Wondering, since you obviously paid a lot for this plugin and it would make sense that you got this basic information?

I know where you’re coming from. If I had paid for this plugin from my spec though, I don’t really know that I would have included documentation of the plugin in the spec if they told me they could do it for less without it.

Since I didn’t pay anything though, and I THINK I might be able to use this on the site, I don’t have a problem with opening up the plugin in the edit screen and reading through it to see what the functions (tags) are along with the style elements to use as my own basic documentation. I do this on most of the plugins I use anyways.

If you open up the plugin and for safety, copy and paste what’s on the edit screen into a text file, you should be able to find all the info you need to get started. Zem_event is very well commented. If you think you don’t know PHP, just look at the file. It’s very readable. Look for the functions and you’ll see an array of the attributes for the tag along with the default values. Try it out on a test site and eventually you’ll know what the plugin can do. Besides, If you try something and can’t get it to work the way you think it’s supposed to, you can always ask a question.

I’ve seen a number of plugins that are developed by folks who are obviously very talented php programmers, but are not the most talented of tech writers. Given that I don’t have to pay for it, I’d much rather have a robust plugin with a minimal help file instead of the opposite, because I get much more frustrated with a well documented plugin that doesn’t work. That’s also the reason I’ve started reading old plugin threads backwards so I can see the post that would indicate that the plugin is abandoned or not updated to the new version of txp yet.

Ren

jstubbs · 2007-02-03 08:14:14

zem wrote:

Enough said I think.

Yes, enough said. What happened before the plugin was released is none of our business. I was just surprised because it seemed that no examples had been given to Mathew – or at least that’s how I read it.

Apologies if my questions sounded aggressive – not what I wanted.

Alex, paying for plugins is a great idea. All the recent ransoms have been met quickly where there has been a real need – ebl_batchupload is one example. The potential downside is when a developer stops supporting or updating the pugin. This seems to happens a lot!

If TeamTextpattern were to develop more paid plugins, we could be sure of the quality, support and operability with the TXP core.

Maybe I should start another thread requesting users to list the plugins/extensions that are needed by the community?

nardo · 2007-02-03 10:14:59

when you’re on an event category list (e.g. /event/?c=Premier-League) … be good to have a tag to return the currently viewed category

just a suggestion for future development if I haven’t missed something already built-in

great work on this, an epic!!

nardo · 2007-02-03 10:45:58

on the individual article page of an event, would you use this in the page template?
<txp:zem_article_event form="zem_event_single" />

Txp puts up a Notice that there is no article tag

When adding <txp:article pgonly=1 /> the individual page template would output the article twice

nardo · 2007-02-03 10:57:34

notice that the ‘label’ attribute automatically adds a colon after the text given it – customisation of that would be good – or just omitted?

—-

to add to that, ‘labeltag’ would be good ;)

Last edited by nardo (2007-02-03 11:23:54)

nardo · 2007-02-03 11:26:27

in the form zem_event_locations – how are the pairs used? is one a ‘name’ and the other a ‘title’ … or is it to allow for shorter ‘names’ on the write tab pulldown?

squaredeye · 2007-02-03 17:42:57

Nardo,
All good questions. I actually don’t know the answers to all these. Lets work together to find out. If you want to email me directly I’d be interested in giving you access to txp.squaredeye.com to help me share new knowledge on the plugin when it arrises. Would you be into that?

per individual articles:

<txp:article status="live" form="zem_event_new" limit="1" />

and the form:

<div class="entry">
<h3>Article Title: <txp:permlink><txp:title /></txp:permlink></h3>
<ul class="event">
<txp:zem_article_event>
<h4>Event Name: <txp:zem_event_name /></h4>
<txp:zem_event_date label="Start Date" wraptag="li" />
<txp:zem_event_finish_date label="Finish Date" wraptag="li"/>
<txp:zem_event_time label="Start Time" wraptag="li" />
<txp:zem_event_finish_time label="Finish Time" wraptag="li"  />
<li><txp:zem_event_url>Event URL</txp:zem_event_url></li>
<li>Location: <txp:zem_event_location /></li>
<li><txp:zem_event_location_url>Map</txp:zem_event_location_url></li>
<p>Short Description: <txp:zem_event_description /></p>
<li>Event contact: <txp:zem_event_email /><li>
<li>Categories: <txp:zem_event_categories /></li>
</txp:zem_article_event>
</ul>
<h3>Article body</h3>
<txp:body />
</div>

Matthew

Textpattern CMS

Textpattern CMS support forum

#61 2007-02-02 01:41:22

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#62 2007-02-02 04:19:32

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#63 2007-02-02 15:13:06

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#64 2007-02-02 18:51:19

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#65 2007-02-02 22:48:54

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#66 2007-02-03 02:12:02

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#67 2007-02-03 08:14:14

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#68 2007-02-03 10:14:59

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#69 2007-02-03 10:45:58

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#70 2007-02-03 10:57:34

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#71 2007-02-03 11:26:27

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

#72 2007-02-03 17:42:57

Re: [plugin] [ORPHAN] zem_event [flexible integrated event management]

Board footer