Menu
▾
▴
tikipro-development — High volume list for discussing the development of TikiPro
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
(123) |
Mar
(202) |
Apr
(121) |
May
(117) |
Jun
(143) |
Jul
(51) |
Aug
(74) |
Sep
(76) |
Oct
(51) |
Nov
(12) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(17) |
Feb
(39) |
Mar
(37) |
Apr
(24) |
May
(10) |
Jun
(30) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Will J. <wj...@ny...> - 2005-09-28 17:19:15
|
Sorry this is a little long....and sorry if its a little nubish, because it is. As some know my goal is to get some sort of wiki-type package working that generates a Google Map on a page and lets you add content and edit it like a wiki. I am looking for some advice on an approach to structuring its database before I start hacking at php code. Google Maps is heavily dependant on javascript and XML - there is some background about Google Maps at the end of this email. But briefly, there are a vew basic parts to google maps. *The Map: a javascript(js) engine *Marker and Polyline Data: which Gmaps likes in the form of XML or js *Marker Content: HTML Each part will also need to have options associated with it. For example for each marker it would be nice to have these kinds of options: *Comments *Type - Normal Marker (as rendered by Google) *Type - PdMarker (a hack style with different features) *Type - GxMarker (another hack style with different features) *Custom Look and feel *Connection to Flickr *Organize as a group My first thoughts on this were, well, maybe each object, a map, a marker, a line could be a little wiki page with javascript content or XML content since everything eventually gets sent up to the map javascript engine. When you choose a feature via the UI the engine would generate the full js code or text with a new Gmap-wiki syntax and that could be saved in a wikipage. But it seems that would make editing it through a UI a real pain! Maybe things should be more structured, more specific. What would seem to make more sense to me is that each object type would have a database table structure and take values from user input. Except that then this seems like it could result in a lot of queries each time a map is loaded. Plus some other questions come up like, what to do if someone wants to upload XML? and how to nest stuff or group stuff, like 100 markers? Perhaps there is another package, that already has a more complex database structure than the wiki, to look at and get some ideas. oh, or best of both worlds, the data gets rendered into javascript that is cached, and the database queries only happen when making the cached js and during editing. Anyway I am looking for some advice on how to store the data and get it up to the user. Hope that all made sense. I have some longer thoughts on what I would like for eventual features on this page: http://mapki.com/index.php?title=GMap_Wikimap_Project and, here is a little more background on Google Maps if you are not already familiar with them. *Google Maps is a javascript app. *Google Maps lets you create markers on a map by submitting lat/lon values. *Markers can also have html content inside popup windows. *Google Maps lets you create lines on a map by submitting an array of lat/lon values. *Google Maps makes good use of XMLHttpRequest for updating info on the map without refreshing. *Refreshing a Google Map page is impracticle if not impossible due to javescript memory leaks. All sorts of details about Google Maps API can be found at and via http://mapki.com Cheers, Will |
|
From: Stephan B. <wol...@ya...> - 2005-06-24 12:01:12
|
Hello all, This is announcement to say we've renamed the project and TikiPro is now called BitWeaver! We've got our first release to the public and we hope you find the quality and performance as impressive as we do. You'll be redirected to http://www.bitweaver.org it if you try to visit the TikiPro site. We encourage you to re-subscribe to the Bitweaver-core mailing list at http://lists.sourceforge.net/lists/listinfo/bitweaver-core and look forward working with you. Regards, The BitWeaver Team |
|
From: Stephan B. <wol...@ya...> - 2005-06-18 13:53:10
|
Are Image Galleries from Bonnie supposed to be upgraded to FishEye in Clyde, during the upgrade process? Stephan |
|
From: William L. <wi...@co...> - 2005-06-14 20:49:14
|
On Sun, 12 Jun 2005, Christian Fowler wrote: > Hi Lester, > >> phpBB is a sidetrack that is detracting from getting a 'finished product'. >> EITHER we are building a framework round Liberty, OR we are building a >> framework for independent packages. Has anybody made a decision yet? >> Because it seems to be fundamental to me! > > A framework inherently allows for multiple solutions. phpBB is very important > to some, and incompatible for others. If you have a phpBB forums install with > thousands of posts, someone else could make an equally founded argument. > > TikiPro was founded on the principle that all needs are considered to have > equal value. We must always be able to support solutions such that all needs > can be addressed, and simultaneously not be forced to adopt someone else's > solution. > > The only forums we have working at the moment are phpBB. TikiWiki forums for > 1.8 (the TikiPro fork branch) where very ugly, and slow and weren't > considered worthy of re-inverting "yet-another forum system". However, times > have changed, and I see three options: > > #1. TikiWiki 1.9 saw a giant leap forward, so I've heard, so. I would be very > interested in looking at maybe moving that forums system forward. > > #2. Drewslater did some awesome work on LibertyComments that are inherently a > light-weight forum system with nested threads. libertyforums/ would make a > fine package. > > #3. Integrate another third board party system. Already some discussion here: > http://www.tikipro.org/forums/viewforum.php?f=10 You may also consider taking a look at fudforum (fudforum.org). Its rather well designed with large number of features (more even then phpbb). Its looks are kind of a cross-bread between tikwiki forums and phpbb. As its already in use by at least two other cms systems so how to integrate it within other system is well known and supported. My personal opinion is that maintaining separate forum system just for tikipro is not the way to go because full forum system is not just threaded comments and involves complexity of management (moderation, post management), integration with other discussions systems (mail lists, newsgroups) and number of other complicated issues - it takes a lot of resources to do and tikipro is not large enough project (yet) to be able to assign enough resources to separate forum subproject. The better way to go is to find well maintained forum system and attempt to integrate it closer with tikipro (working with its developers if possible) which may include changing its content data to be able to handle tiki and be able to reference other tikipro elements. Whatever you decide I'll support but for now I'm sticking with phpbb because its the most well developed forum system that can be used with tikipro and I would hope that support for phpbb will continue to exist unless you're able to find comparable (in administration and other features) forum system and support migration from phpbb. --- William Leibzon mailto: wi...@co... Anti-Spam and Email Security Research Worksite: http://www.elan.net/~william/emailsecurity/ Whois & DNS Network Investigation Tools: http://www.completewhois.com |
|
From: Stephan B. <wol...@ya...> - 2005-06-13 07:50:47
|
--- Christian Fowler <sp...@vi...> wrote: > the time consuming > part is implementing all the great features (move topic, hot topic, lock > topic, sticky topic, moderators, etc.) of mature forums code. Can we slice-n-dice from the existing tikiforums code? Stephan Send instant messages to your online friends http://au.messenger.yahoo.com |
|
From: Christian F. <sp...@vi...> - 2005-06-13 06:06:37
|
I just created the CLYDE branch in CVS. This means #1 - A final release candidate ( http://www.tikipro.org/builds/tikipro_clyde_fc1.tar.gz ) available for your downloading. Please download, TEST TEST TEST, [url=http://sourceforge.net/tracker/?group_id=101599&atid=630083]report any bugs[/url] #2 - If you are running off of CVS, you need to "cvs update -r CLYDE" in your cvs checkout. [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org |
|
From: Christian F. <sp...@vi...> - 2005-06-13 05:08:15
|
wiki comments, blog comments and more. they all use the same code. Making a root content type of "forum post" would be very easy. the time consuming part is implementing all the great features (move topic, hot topic, lock topic, sticky topic, moderators, etc.) of mature forums code. On Sun, 12 Jun 2005, James H. Thompson wrote: > >> #2. Drewslater did some awesome work on LibertyComments that are >> inherently a light-weight forum system with nested threads. libertyforums/ >> would make a fine package. > > Is this running somewhere we can look at it? > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org |
|
From: James H. T. <jh...@lj...> - 2005-06-13 04:48:19
|
>#2. Drewslater did some awesome work on LibertyComments that are=20 >inherently a light-weight forum system with nested threads. = libertyforums/=20 >would make a fine package. Is this running somewhere we can look at it? |
|
From: Stephan B. <wol...@ya...> - 2005-06-13 03:04:04
|
On Sun, 2005-06-12 at 22:53 -0400, Christian Fowler wrote: > #2. Drewslater did some awesome work on LibertyComments that are > inherently a light-weight forum system with nested threads. libertyforums/ > would make a fine package. For what its worth, LibertyForums sounds like a fantastic replacement for TikiForums and default forum system to replicate functionality lost. Stephan |
|
From: Christian F. <sp...@vi...> - 2005-06-13 02:53:36
|
Hi Lester, > > phpBB is a sidetrack that is detracting from getting a 'finished product'. > EITHER we are building a framework round Liberty, OR we are building a > framework for independent packages. Has anybody made a decision yet? Because > it seems to be fundamental to me! A framework inherently allows for multiple solutions. phpBB is very important to some, and incompatible for others. If you have a phpBB forums install with thousands of posts, someone else could make an equally founded argument. TikiPro was founded on the principle that all needs are considered to have equal value. We must always be able to support solutions such that all needs can be addressed, and simultaneously not be forced to adopt someone else's solution. The only forums we have working at the moment are phpBB. TikiWiki forums for 1.8 (the TikiPro fork branch) where very ugly, and slow and weren't considered worthy of re-inverting "yet-another forum system". However, times have changed, and I see three options: #1. TikiWiki 1.9 saw a giant leap forward, so I've heard, so. I would be very interested in looking at maybe moving that forums system forward. #2. Drewslater did some awesome work on LibertyComments that are inherently a light-weight forum system with nested threads. libertyforums/ would make a fine package. #3. Integrate another third board party system. Already some discussion here: http://www.tikipro.org/forums/viewforum.php?f=10 There is nothing I would love more than to have an alternative phpBB available that we could offer. I support any initiatives in this area, though have little cycles to burn on it myself. - spider > > -- > Lester Caine > ----------------------------- > L.S.Caine Electronic Services > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge > track? > If you want to score the big prize, get to know the little guy. Play to win > an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Tikipro-development mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikipro-development > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org |
|
From: Stephan B. <wol...@ya...> - 2005-06-13 02:03:21
|
On Sun, 2005-06-12 at 21:56 -0400, Christian Fowler wrote: > Welcome back! First, if your BONNIE -> CLYDE upgrade "fails miserably", we > really need those bugs logged asap. The upgrader has been working great on > all the dumps I have tested with, even voip-info.org's massive site. Ok - I will try again soon and log bugs as necessary. > If you are proposing an API, I think that will generate a lot of code that > we will have to fix. Decent SQL statements should be able to most > accurately handle everything we need. No, no :) - no API's - just a per package migrations option, maybe a menu item of dedicated per package migration interface - if its possible. Stephan |
|
From: Christian F. <sp...@vi...> - 2005-06-13 01:56:54
|
Hi Wolffy, Welcome back! First, if your BONNIE -> CLYDE upgrade "fails miserably", we really need those bugs logged asap. The upgrader has been working great on all the dumps I have tested with, even voip-info.org's massive site. upgrade_inc.php is technically a migration system. The code is extremely flexible, and can handle any arbitrary source and destination revision for any and all databases we support. I suppose I don't understand how your proposal is different. If you are proposing an API, I think that will generate a lot of code that we will have to fix. Decent SQL statements should be able to most accurately handle everything we need. - spider On Sun, 12 Jun 2005, Stephan Borg wrote: > Had some thoughts about Package Upgrade/Migration that I'd like to > share. > > How easy would it be to implement a per package upgrade/migration > system? Using the same code that is used in the Install/Upgrade process, > but on a per package basis. > > I have found that when I go to beta test my existing Bonnie site, which > is feature packed - the upgrade process fails miserably and all I really > want to do is migrate wiki pages. > > The other advantage to this method (albeit slower) is each package would > get 'verified' as it is imported into Liberty, through standard sanity > checking using the API, rather than direct database modifications (which > are a lot faster). Personally I'm happy to sacrifice speed for > verification of migration. > > Any thoughts on the subject? > > Stephan > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Tikipro-development mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikipro-development > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org |
|
From: Stephan B. <wol...@ya...> - 2005-06-12 09:36:52
|
--- Lester Caine <le...@ls...> wrote: > I am STILL not convinced that Liberty is stable enough to start doing > that, and more important - if it is even going to be compatible with > what *I* need to achieve. What parts of Liberty do you consider unstable? Personally, I don't consider certain parts of the core stable (LDAP authentication, cookie domains, remember me, etc), but when it comes to release I can live with it. > I don't want to plow more months of work in if I can't achieve a working > end point quickly, and at present the 'API' for even working with > Liberty does not seem to exist? Or has not been documented by someone yet? :) > phpBB is a sidetrack that is detracting from getting a 'finished > product'. EITHER we are building a framework round Liberty, OR we are > building a framework for independent packages. Has anybody made a > decision yet? Because it seems to be fundamental to me! As was mentioned previously, I totally agree with dropping phpBB as part of our release and ensuring TikiForums is Libertised and in a working form before Dillenger (if not before Clyde release - doubtful). I also totally agree that development by those using phpBB within TikiPro continues, including remaining a part of www.tikipro.org - to show the public that we are not joking about integration with third-party packages. We decided to call ourselves a web application framework. We claim to have a focus on integration of other packages. And we also have built a fantastic content management framework - I don't see any reason why we can't achieve all of them at the same time. :) Stephan Send instant messages to your online friends http://au.messenger.yahoo.com |
|
From: James H. T. <jh...@lj...> - 2005-06-12 08:42:25
|
My personal preference would also be to drop PHPBB and use a TPized = version of TikiWiki Forums. If TikiPro is going to complete with intergrated systems like Zope and = Drupal, then its going to need tight integration between the various = pieces, and common use of content between them. I don't see how that = can be accomplished with a 3rd party forum package. Jim James H. Thompson jh...@lj... ----- Original Message -----=20 From: Lester Caine=20 To: tik...@li...=20 Sent: Saturday, June 11, 2005 10:26 PM Subject: Re: [Tikipro-development] Package Maintainers xing wrote: >> I need a forum as a matter of urgency, and at present I am = seriously =20 >> considering dropping back to tikiwiki because of time pressures. =20 >> Currently there is a considerable lack of facilities that were=20 >> working only a few months ago, and currently I am not convinced = that=20 >> clyde will be nailed down enough to spend time 're-fixing' those=20 >> packages that I had already got working !!! >=20 > i am not a database person and i don't know what breaks the firebird = =20 > compatability. it might be useful if you could post a page on tp.o =20 > entailing all changes you have to make on a regular basis to get = stuff =20 > working for you. it might help us code this thing in a firebird=20 > accepted way. The database stuff is not too difficult at all. Usual niggles are=20 missing back quotes, tweaks to SQL to tidy JOIN structure, and=20 standardising on things like - LIKE - in a generic way. Most of the=20 generic stuff is now done in the TikiDB library and as long as THAT is = used, rather than had coding database specific SQL we will be OK. My main grumble at the moment is nothing to do with Firebird! I have a nice working package with contacts, calendar, appointments = and=20 ticketing, which works very fast. But NONE of it is compatible with = the=20 current clyde core and the whole lot needs to be re-written! I am STILL not convinced that Liberty is stable enough to start doing=20 that, and more important - if it is even going to be compatible with=20 what *I* need to achieve. So do I just move back to pre-Liberty setup and carry on from there -=20 because I *DO* have a working system. Certainly I can see a hell of a=20 lot of work if I want all that functionality in the current clyde = build :( The problem is a simple fundamental one ;) I just see the content as content. The content of a blog, wiki, forum=20 message, article, comment, description for a picture, etc are all the=20 same thing and can be edited with the same editor. We then just call = up=20 a structure that puts those elements together as required - AND USES = ANY=20 ELEMENT - So Liberty cuts right across every package and should = provide=20 a generic set of tools, which I am still not seeing - yet ;) WHAT *IS* the difference between the tree of comments added to a wiki=20 page and a forum thread ? I don't want to plow more months of work in if I can't achieve a = working=20 end point quickly, and at present the 'API' for even working with=20 Liberty does not seem to exist? phpBB is a sidetrack that is detracting from getting a 'finished=20 product'. EITHER we are building a framework round Liberty, OR we are=20 building a framework for independent packages. Has anybody made a=20 decision yet? Because it seems to be fundamental to me! --=20 Lester Caine ----------------------------- L.S.Caine Electronic Services ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you = shotput a projector? How fast can you ride your desk chair down the office = luge track? If you want to score the big prize, get to know the little guy. =20 Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20 _______________________________________________ Tikipro-development mailing list Tik...@li... https://lists.sourceforge.net/lists/listinfo/tikipro-development |
|
From: Lester C. <le...@ls...> - 2005-06-12 08:22:12
|
xing wrote: >> I need a forum as a matter of urgency, and at present I am seriously >> considering dropping back to tikiwiki because of time pressures. >> Currently there is a considerable lack of facilities that were >> working only a few months ago, and currently I am not convinced that >> clyde will be nailed down enough to spend time 're-fixing' those >> packages that I had already got working !!! > > i am not a database person and i don't know what breaks the firebird > compatability. it might be useful if you could post a page on tp.o > entailing all changes you have to make on a regular basis to get stuff > working for you. it might help us code this thing in a firebird > accepted way. The database stuff is not too difficult at all. Usual niggles are missing back quotes, tweaks to SQL to tidy JOIN structure, and standardising on things like - LIKE - in a generic way. Most of the generic stuff is now done in the TikiDB library and as long as THAT is used, rather than had coding database specific SQL we will be OK. My main grumble at the moment is nothing to do with Firebird! I have a nice working package with contacts, calendar, appointments and ticketing, which works very fast. But NONE of it is compatible with the current clyde core and the whole lot needs to be re-written! I am STILL not convinced that Liberty is stable enough to start doing that, and more important - if it is even going to be compatible with what *I* need to achieve. So do I just move back to pre-Liberty setup and carry on from there - because I *DO* have a working system. Certainly I can see a hell of a lot of work if I want all that functionality in the current clyde build :( The problem is a simple fundamental one ;) I just see the content as content. The content of a blog, wiki, forum message, article, comment, description for a picture, etc are all the same thing and can be edited with the same editor. We then just call up a structure that puts those elements together as required - AND USES ANY ELEMENT - So Liberty cuts right across every package and should provide a generic set of tools, which I am still not seeing - yet ;) WHAT *IS* the difference between the tree of comments added to a wiki page and a forum thread ? I don't want to plow more months of work in if I can't achieve a working end point quickly, and at present the 'API' for even working with Liberty does not seem to exist? phpBB is a sidetrack that is detracting from getting a 'finished product'. EITHER we are building a framework round Liberty, OR we are building a framework for independent packages. Has anybody made a decision yet? Because it seems to be fundamental to me! -- Lester Caine ----------------------------- L.S.Caine Electronic Services |
|
From: xing <xi...@sy...> - 2005-06-12 07:50:28
|
> But what is required is a GOOD framework that can form the basis for > that work, and Tikipro - while still having a few rough edges - provides > a nice framework which is almost acceptable out of the box. EXCEPT > packages are included in the basic install that are NOT ready for > general use. > > PLEASE can we drop phpBB and anything else that does not work with ALL > engines on the install list, and only allow them to be 'extra' > downloads, then perhaps we can start looking at what *IS* finished for > general distribution? i agree that 3rd party packages should not be part of the core distribution. there might be licensing hiccups (such as the default phpBB theme) and they generally don't take advantage of liberty and thus have different searches, upload paths, etc. > > I need a forum as a matter of urgency, and at present I am seriously > considering dropping back to tikiwiki because of time pressures. > Currently there is a considerable lack of facilities that were working > only a few months ago, and currently I am not convinced that clyde will > be nailed down enough to spend time 're-fixing' those packages that I > had already got working !!! i am not a database person and i don't know what breaks the firebird compatability. it might be useful if you could post a page on tp.o entailing all changes you have to make on a regular basis to get stuff working for you. it might help us code this thing in a firebird accepted way. > > PLEASE can we put a six inch nail in the core engine so that we CAN > actually maintain any other package !!! xing |
|
From: Lester C. <le...@ls...> - 2005-06-12 07:44:37
|
Stephan Borg wrote: >>PLEASE can we drop phpBB and anything else that does not work with ALL >>engines on the install list, and only allow them to be 'extra' >>downloads, then perhaps we can start looking at what *IS* finished for >>general distribution? > > I have the same problem - I am not a phpBB user and don't intend to become one, > with my legacy TW1.8 install and use of TikiForums are major requirement for me > to move to Clyde. I'm not alone then ;) > I agree its painful, although I'm not sure (apart from you making compatible > yourself) what the alternatives are? Like Articles, it required at least 2 core > developers to *need* it, for it to be migrated to Clyde. > > Apart from all this, I'm not sure how this reflects on the Package Maintainers > proposal. :) We need package maintainers for the packages we need :) I'm quite happy to rebuild a number of packages yet again, but I need to know that I am not wasting my time :( The current Liberty structure is very nice, and while packages can be completely isolated, things like CALENDAR where I can list all additions to Liberty and filter to view just one type is looking good. But since phpBB is not part of Liberty then it can't be viewed with the rest of the content. As far as I can see, everything is in place for us to be able to call up a structure that consists of elements from each package? (which is what *I* need next) And that structure can also indicate how each element should be displayed? Articles, Blogs, Wiki, Forum and Comments are all the same thing so WHY are we making this sooo complex? -- Lester Caine ----------------------------- L.S.Caine Electronic Services |
|
From: Stephan B. <wol...@ya...> - 2005-06-12 07:23:17
|
--- Lester Caine <le...@ls...> wrote: > PLEASE can we drop phpBB and anything else that does not work with ALL > engines on the install list, and only allow them to be 'extra' > downloads, then perhaps we can start looking at what *IS* finished for > general distribution? I have the same problem - I am not a phpBB user and don't intend to become one, with my legacy TW1.8 install and use of TikiForums are major requirement for me to move to Clyde. > > I need a forum as a matter of urgency, and at present I am seriously > considering dropping back to tikiwiki because of time pressures. > Currently there is a considerable lack of facilities that were working > only a few months ago, and currently I am not convinced that clyde will > be nailed down enough to spend time 're-fixing' those packages that I > had already got working !!! I have not made the move past beta testing Clyde, and probably won't until TikiForums is working - but moving to Clyde is not a priority at this point and hence I cannot guarantee any effort in making TikiForums Clyde compatible. I agree its painful, although I'm not sure (apart from you making compatible yourself) what the alternatives are? Like Articles, it required at least 2 core developers to *need* it, for it to be migrated to Clyde. Apart from all this, I'm not sure how this reflects on the Package Maintainers proposal. :) Stephan Send instant messages to your online friends http://au.messenger.yahoo.com |
|
From: Lester C. <le...@ls...> - 2005-06-12 06:57:32
|
Stephan Borg wrote: > I've written up a proposal on tp.o about Package Maintenance (see > http://www.tikipro.org/wiki/PackageMaintainer ), which I submit for > comments. > > With regard to this proposal, whats the general consensus on on this > list about Package Maintainer teams? I think a few agreements on fundamentals would be nice first? I want a system that allows me to add and remove the modules I want, and updating a single package ( other post ) seems a good way to go, but currently, the inclusion of phpBB as the forum package is causing a major pain since it is totally unusable in Firebird! *SO* - since many of the people I am trying to 'convert' NEED forum as part of the total package - what do I do. I know not many of you are interested in Firebird, but we have 20 years worth of 'history', and with all the crap going on in the windows development environment, a LOT of those users are currently looking for an alternative, which PHP provides. We can run Firebird/PHP applications in parallel with existing systems while changing, and everything works nicely. But what is required is a GOOD framework that can form the basis for that work, and Tikipro - while still having a few rough edges - provides a nice framework which is almost acceptable out of the box. EXCEPT packages are included in the basic install that are NOT ready for general use. PLEASE can we drop phpBB and anything else that does not work with ALL engines on the install list, and only allow them to be 'extra' downloads, then perhaps we can start looking at what *IS* finished for general distribution? I need a forum as a matter of urgency, and at present I am seriously considering dropping back to tikiwiki because of time pressures. Currently there is a considerable lack of facilities that were working only a few months ago, and currently I am not convinced that clyde will be nailed down enough to spend time 're-fixing' those packages that I had already got working !!! PLEASE can we put a six inch nail in the core engine so that we CAN actually maintain any other package !!! -- Lester Caine ----------------------------- L.S.Caine Electronic Services |
|
From: Stephan B. <wol...@ya...> - 2005-06-12 05:39:45
|
Hi all, I've written up a proposal on tp.o about Package Maintenance (see http://www.tikipro.org/wiki/PackageMaintainer ), which I submit for comments. With regard to this proposal, whats the general consensus on on this list about Package Maintainer teams? Stephan |
|
From: Stephan B. <wol...@ya...> - 2005-06-12 04:37:28
|
Hi all, Is anyone on the list a source of more information regarding SDLC's and applicability to the TikiPro project? I've just sat an IS Auditing exam, where I had to learn all about SDLC's and couldn't help but wonder if implementing such a cycle for TikiPro was a positive move. I've written up a little blurb on tp.o about SDLC's <http://www.tikipro.org/wiki/System+Development+Life+Cycle+%28SDLC%29> and with a little lateral thinking, I think we can apply it to our project. Maybe we could get a feel of opinion about it on the list? Stephan |
|
From: Stephan B. <wol...@ya...> - 2005-06-11 23:37:20
|
Had some thoughts about Package Upgrade/Migration that I'd like to share. How easy would it be to implement a per package upgrade/migration system? Using the same code that is used in the Install/Upgrade process, but on a per package basis. I have found that when I go to beta test my existing Bonnie site, which is feature packed - the upgrade process fails miserably and all I really want to do is migrate wiki pages. The other advantage to this method (albeit slower) is each package would get 'verified' as it is imported into Liberty, through standard sanity checking using the API, rather than direct database modifications (which are a lot faster). Personally I'm happy to sacrifice speed for verification of migration. Any thoughts on the subject? Stephan |
|
From: Lester C. <le...@ls...> - 2005-06-09 17:38:31
|
Wascally Wabbit wrote: > Maybe it just me, but entering http://www.tikipro.org/forums/ > generates the following page fyi. Try clearing your cookies for www.tikipro.org It's fine for me! -- Lester Caine ----------------------------- L.S.Caine Electronic Services |
|
From: Christian F. <sp...@vi...> - 2005-06-09 17:32:28
|
Thanks Wabbit. Forget to check for people are are *not* admins. Should be fixed now. Please post back asap if it appears things are horked. On Thu, 9 Jun 2005, Wascally Wabbit wrote: > Maybe it just me, but entering http://www.tikipro.org/forums/ > generates the following page fyi. > > ---------- [ SNIP ] ---------- > phpBB : Critical Error > > Error creating new session > > DEBUG MODE > > SQL Error : -1 ERROR: syntax error at or near ")" at character 258 > > INSERT INTO phpbb.sessions (session_id, session_user_id, session_start, > session_time, session_ip, session_page, session_logged_in, session_admin) > VALUES ('ef41ddea8e60a36546630e039996682b', 266, 1118337154, 1118337154, > '18ee4307', 5, 1, ) > > Line : 175 > File : /home/tikipro/CLYDE/forums/includes/sessions.php > > > The Wabbit > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge > track? > If you want to score the big prize, get to know the little guy. Play to win > an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Tikipro-development mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikipro-development > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org |
|
From: Wascally W. <was...@ea...> - 2005-06-09 17:14:21
|
Maybe it just me, but entering http://www.tikipro.org/forums/ generates the following page fyi. ---------- [ SNIP ] ---------- phpBB : Critical Error Error creating new session DEBUG MODE SQL Error : -1 ERROR: syntax error at or near ")" at character 258 INSERT INTO phpbb.sessions (session_id, session_user_id, session_start, session_time, session_ip, session_page, session_logged_in, session_admin) VALUES ('ef41ddea8e60a36546630e039996682b', 266, 1118337154, 1118337154, '18ee4307', 5, 1, ) Line : 175 File : /home/tikipro/CLYDE/forums/includes/sessions.php The Wabbit |
2 messages has been excluded from this view by a project administrator.