42
Quote:
DCrussader wrote:
From bad to worst (Nuke to WP), let's make it like Drupal, it's a solid-rock CMS which no one use from ages, the only CMS which uses NODE instead of Article, well 2nd using Weight instead of Ordering, Taxonomy Term for Sub-category, and adding GNU Gettext.
I think you misunderstood me. I'm not looking after WP way of doing translations. But I think the standards they propose can be applied to Xoops.
Quote:
X-1.0.zip downloaded %1s (one download)
X-1.0.zip downloaded %2s (many downloads)
Seems you agree with using placeholders.
Quote:
2nd point - no idea what for will be used as language files, INI, POT, PHP or something else ? How much alphas will go out ?
It does not depend only on me. I'm thinking seriously on using INI files and have the code using it on alpha3. Perhaps the translate class and some demos can be release on alpha2, for review.
Quote:
3rd.....
Several different threads are opened for 2.6 without mentioning simple task tree:
I find organization a very complex subject. The core team is working very fine without using 'simple' tasks. We have pending simple tasks on sourceforge for years now.
Quote:
Quote:
How the decision was taken for this ? XOOPS was "community driven", where was the Poll regarding all alternatives ? I think something like this was used in J! 1.0 and removed by own class in 2.5, so the users can make PDF of any content type from the sites in Cyrillic.
htm2pdf contains the tcpdf library so the core team thought it would be a good addition. We can't discuss every subject with the community. If this library does not work on Cyrillic sites we will definitely look for other solutions. We are on alpha stage, we did not test this library on all contexts and we do expect users to report problems.
Quote:
Quote:
- In order to easily add content "out of the box" .
This means nothing - content like the default option in Baned CMS ? Wow if is this, amazing, just amazing....
I can't tell if you are being sarcastic. Since 'page' module is delivered with the core package it will allows users to publish pages without having to look around for content modules.
Quote:
Quote:
- This system allow to create all kind of menus.
Simple Menu Manager or something like Solo Menu module ?
Something like Solo Menu module. It is a refactoring of Mymenus module which was based on the multimenus module by Solo.
Quote:
File Manager/Image Manager ? Maybe in Alpha 5 on random pick without votes ?
Content/Blocks editor - SC, tinyMCE (yack), CK, default used in XOOPS 2.5 ?
Image manager will be just a "move from core to module". We will be looking at features at latter stages. Being modules/extensions, other developers can deliver their own versions which can latter be used as the official module.
I don't know which editor we will be using has default.
Quote:
Alpha 3 looks like Beta 1
And Final 2.6.0 around Christmas 2013 or Q2 of 2014.... (but better late, then never 
)
We are aiming for latter dates so we don't disappoint the community. I hope we can do this faster then the roadmap suggests.
Quote:
Won't mention my favorite - Sign up/in, Weight and a lot of other termins not used anywhere else except in Drupal/XOOPS 2.5/WP, which making system not only "non-user friendly" but also not understandable...
I think we will be able to deliver a more user/developer/translator/designer friendly XOOPS. And by 'we' I mean users/developers/translators/designers.
