cotonti.com : DHTML Js Calendar https://www.cotonti.com Last topic posts Cotonti en Wed, 08 Apr 2026 21:20:14 -0000 booka Kort, that JS calendar just an example of user friendly feature that Cotonti is missed to became popular CMS. Right now when we have a lot of different CMS/CMF around - our CMS must be not just fastest or lightest - but most user friendly and original.

Mostly users now want to start new sites ASAP and after that extend their sites using live examples and learn on it.]]> Wed, 05 May 2010 00:57:18 -0000 donP Otherwise, I can consider the great and hard work to port my site to another CMF sustained by a most open and collaborative community.]]> Tue, 04 May 2010 23:24:54 -0000 Kort Tue, 04 May 2010 22:41:18 -0000 donP # Kort : ...But that's not what Cotonti is made for...
If Cotonti claims to be a CMF then we must study it to support any task or situation.

Kort:
...requiring that jq calendars or datepickers are embedded into the core...
Me and Koradhil were just asking to make the core more simple and capable of hooking every plugin or jQuery script a webmaster needs for his situation, not to include a datepicker in the package.

Kort:
...10-15 times is nonsense and you understand it yourself...
It would be a nonsense only if you have so much time to waste everytime you have to set a date setting FIVE select fields you could instead set with a simple click on a calendar.

Kort:
You've been shown a way to deal with your specific situation: if you can't get the job done it doesn't mean it is impossible.

When a developer community becomes so hostile and one-sided is the beginning of the end ... I think we'll never see Cotonti expansion between CMF :(]]> Tue, 04 May 2010 21:28:13 -0000 Kort # donP : Ah no?! Everytime a user wants to insert a New in homepage and decide when that New has to appear and when would diappear... this is the most important activity for a frontpage site with many contibutors writing contents. At least 10-15 times a day! Thinking big is good. But that's not what Cotonti is made for. You do not manipulate dates or deal with dates to the extent requiring that jq calendars or datepickers are embedded into the core. 10-15 times is nonsense and you understand it yourself. You've been shown a way to deal with your specific situation: if you can't get the job done it doesn't mean it is impossible.]]> Tue, 04 May 2010 13:26:35 -0000 ez Lets make a plugin for it with custom tags something like {PAGEADD_FORM_EXPIRE_NICEGUI} for the nice looking GUI, with on the backend (hidden) the original cotonti stuff...

The two fields idea.... (I do not like that personally, this is waiting for shit to happen)

I do not have the time for it right now, maybe... later]]> Tue, 04 May 2010 05:46:13 -0000 esclkm
find
{PAGEADD_FORM_EXPIRE}
make smth like :
<div class="hide_date">{PAGEADD_FORM_EXPIRE}</div>
than with help of jquery hide block
next step^ find all elements of this date by select name
it will be something like
function updateSelected(dates) {
$('[name=selectedMonth]').val(dates.length ? dates[0].getMonth() + 1 : '');
$([name=selectedDay]').val(dates.length ? dates[0].getDate() : '');
$('[selectedYear]').val(dates.length ? dates[0].getFullYear() : '');
checkLinkedDays(); // Disable invalid days
blah blah blah

it is not hard/ it is not plugin. It is just TEMPLATE.]]> Tue, 04 May 2010 05:33:04 -0000 donP booka:
I now Cotonti since LDU... Totally from my point of view (user) - nothing changed in general. It still looks like something made on kneels - it has a potential and can be used to run GREAT sites, but it is not something attractive from marketing point of view. Looks like it lives for itself - to be fastest, with minimum weight, with big potential, BUT... I totally agree with these considerations!

In Cotonti HomePage we can read:
  • Modular and extensible with Modules and Plugins.
  • Layout separated from logic. Templates render fast, no PHP skills required.
  • Client-side magic with on-board jQuery.
  • Easy to understand, easy to customize.
I think we have to make more TRUE these statements]]> Tue, 04 May 2010 05:24:08 -0000 booka
I understand that core development is something away from User Friendly religion, but it must be Plugin-maker Friendly. All modifications, like date pickers or something must be done without changing of the core.

From the other hand - most of developers told about how to achieve more clients, how to apply our CMS to more sites. To do that first off all it must be user friendly, it must support auto installation like Windows or Mac installer, it must be flexible and support things that didn't require any coding just from the box: Galleries, Blogs, Forums, Forms which are not required any reloads etc. And for sure it must has a lot (about 10 to 20) perfect WEB 2.0 skins just out from the box. Look at this site - even it doesn't looks good, Neocrome.net looks much better for now.

I'm not a perfect coder and I'm not perfect skinmaker - so you can freely forget about my thoughts. But for example - right now I need to start new ecommerce project. I can install Magento - spent few month to optimize it for local realms or find some coder to do that. But I can go to WebAssyst Shop-Script - it has less functionality - but it is easy, it has a lot of user friendly things and I can just download and begin to use it. Yes - it will cost some money, but how much money I can loose while playing with heavy code even if it can provide me with more functionality?

Добавлено 3 Минуты спустя:

I now Cotonti since LDU... Totally from my point of view (user) - nothing changed in general. It still looks like something made on kneels - it has a potential and can be used to run GREAT sites, but it is not something attractive from marketing point of view. Looks like it lives for itself - to be fastest, with minimum weight, with big potential, but...]]> Tue, 04 May 2010 05:11:17 -0000 donP Kort:
manipulating dates is not something you do often with Cotonti Ah no?! Everytime a user wants to insert a New in homepage and decide when that New has to appear and when would diappear... this is the most important activity for a frontpage site with many contibutors writing contents. At least 10-15 times a day!

Me and Koradhil were only saying that, for implementing plugins (I can make my own like I've ever done, from LDU 600, I don't need a ready-made solution) we have to make the core able to hook them...
I was remarking that, FOR EXAMPLE, the actual page-date/begin/expire is very hard to integrate with a plugin (not only a JsDatepicker) if we have FIVE select-fields to set a single date!

ez:
So, what solution should/can we make?
Koradhil's one:
Koradhil:
supporting two formats: seperate fields (existing) and a combined field, allowing for developers to choose between input formats.
]]> Tue, 04 May 2010 05:01:08 -0000 ez I agree with a lot off arguments above... (there are pro's and con's for everything)

I too think we could use some nice things like datepickers and other stuff, but it should be like a piece off Lego (a building block)

I am a very strong believer of a small core and plugins to expand/extend to the users needs...
I even think that most parts should be plugins... (but that is just my opinion)

Maybe the best solution is solid core components that are useable/flexible for integrating all kinds
off nice GUI stuff. Let's think about that....

Personally I haven't looked at things like GUI (JS)datepickers, but now that this discussion is there... hmmmmm I would love to see them.. (but not risking something..)

So, what solution should/can we make?]]> Tue, 04 May 2010 04:31:27 -0000 Kort As regards calendars/datepickers, manipulating dates is not something you do often with Cotonti. I'd even say, you do not normally manipulate dates in Cotonti. But if you do need it, make a plugin and do not request immediate core adjustment.]]> Tue, 04 May 2010 03:01:58 -0000 donP
It's mostly this (your) way of thinking and develop Cotonti that makes it so obscure and remote to simple users.
I'm a webmaster, I'm quite skilled to write my contents as I want, also directly in HTML, I'm clever enough to mantain my personal website also directly making changes inside PHP code and core-hacking the origninal script... but, if you want to setup a website and leave it for a not very expert client, or just allow everyone to participate to a website by inserting contents, Cotonti is actually the less intuitive interface we can find among CMS around!

Kort:
Integrating 3rd party scripts is a job for plugin-maker
Yes, but plugin makers must have te ability to interact with a simple code, not a cryptic core so difficult to interface! (as a date-insert with FIVE select fields)]]> Tue, 04 May 2010 02:20:07 -0000 Kort Mon, 03 May 2010 22:35:56 -0000 esclkm http://trac.cotonti.com/ticket/483 - Koradhil - Do you see cotonti history? What is it? You think - you make. it is just very bad manner in my mind.

I think may be not bad way is general input for date - but what do you say about date format? or about how to check this string for the right value]]> Mon, 03 May 2010 21:02:41 -0000 donP 
// Update three select controls to match a datepicker selection 
function updateSelected(dates) { 
    $('#selectedMonth').val(dates.length ? dates[0].getMonth() + 1 : ''); 
    $('#selectedDay').val(dates.length ? dates[0].getDate() : ''); 
    $('#selectedYear').val(dates.length ? dates[0].getFullYear() : ''); 
    checkLinkedDays(); // Disable invalid days 
} 
 
$('#selectedPicker').datepick({ 
    minDate: '01/01/2001', maxDate: '12/31/2010', 
    alignment: 'bottomRight', onSelect: updateSelected, 
    showTrigger: '#calImg'}); 
 
// Update datepicker from three select controls 
$('#selectedMonth,#selectedDay,#selectedYear').change(function() { 
    $('#selectedPicker').datepick('setDate', new Date( 
        $('#selectedYear').val(), $('#selectedMonth').val() - 1, 
        $('#selectedDay').val())); 
});
but where and how can we insert that in Cotonti without core hacks?

Adn... why you assigned the ticket to Renaissance?]]> Mon, 03 May 2010 20:15:54 -0000 GHengeveld original datepicker documentation.

Still, I've created a ticket since it will allow for more flexibility in general (entering a date as plaintext for example). See ticket 483.]]> Mon, 03 May 2010 19:41:16 -0000 esclkm Your Super Calendars are also Js - I think it is very for plugs, templates, but not core! - http://trac.cotonti.com/ticket/366]]> Mon, 03 May 2010 19:29:38 -0000 donP ]]> Mon, 03 May 2010 19:01:20 -0000 GHengeveld # donP : But the problem is the integration with Cotonti, 'cause, actually, we have FIVE (!!!) select fields to record ONE date field!
We would hardly change core and .tpl files... :/ That would be easily solved by supporting two formats: seperate fields (existing) and a combined field, allowing for developers to choose between input formats.

I've found that using strftime and strptime are the easiest and most flexible way to do this. Of course parsing dates for display will still require a custom function for localisation.

I'll add a ticket for this.]]> Mon, 03 May 2010 17:51:23 -0000 donP http://jqueryui.com/demos/datepicker/ ;)
Good, and using jQuery...
But the problem is the integration with Cotonti, 'cause, actually, we have FIVE (!!!) select fields to record ONE date field!
We would hardly change core and .tpl files... :/]]> Sun, 02 May 2010 20:54:47 -0000 booka http://jqueryui.com/themeroller/]]> Sun, 02 May 2010 20:38:51 -0000 donP A first step would be this great DHTML Calendar to fill date fields everywhere (pages, user profiles and so on).]]> Sun, 02 May 2010 20:21:49 -0000