161
GIJOE
Re: Pical vs. Agendax
  • 2003/11/21 1:23

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


Although I'm not interested about such meaningless comparison, I'm interested in the feature of PostCalendar.

I've never used PostCalendar yet, because PostNuke is a minor CMS in Japan.

Tell me which feature of PostCalendar is better than piCal.

As I've already implemented most of requested features in www.xoopscube.jp, I'll be able to implement any features without irrelevant to calendar like random image.



162
GIJOE
Re: PiCal - Image's "alt" tag does not display correctly
  • 2003/11/20 23:09

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


I can't see what you mean well.
Do you tried the skin feature?

Anyway, {MB_PREV_YEAR} in *.tmpl.html should be replaced the language constant '_PICAL_MB_PREV_YEAR' by patTemplate.
(* means daily, weekly, monthly, yearly)

piCal don't use Smarty but use patTemplate.

Or, do you want to use {MB_PREV_YEAR} in MiniCalendar?
If so, it is necessary to add some assignments into piCal.php, because the original MiniCalendar don't assign MB_PREV_YEAR.



163
GIJOE
Re: X2 Core: [code] tag's output correction
  • 2003/11/20 3:09

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


This serious bug about the [ code] tag still remains in 2.0.5 or the recent CVS.

In 2.0.5, stripslashes() has been removed from $replacements for inside [ code].
But no essential improvement.
This cause more escape " inside [ code] under 'HTML allowed'.

Mr.Ryuji examined the operation of /e modifier of preg_replace(),
and he has finally discovered the best method.

See B-wiki of XOOPS Hackers 2 in Japan.

Of course, these hack codes also solve following problems about [ code] tag:
- Destroying 'newline' - this makes to fail Copy & Paste (IE).
- Influenced by makeClickable() - this destroys some kind of php codes.

I strongly insist that Ryuji's hack codes should be taken into XOOPS CORE CVS.

Thanks!



164
GIJOE
Re: piCal header
  • 2003/11/14 8:49

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


Perhaps, you didn't edit a proper file.

Which file do you change ?
The template file of monthly calendar is monthly.tmpl.html.

If you mean a block of monthly calendar, the template is block_monthly.tmpl.html.



165
GIJOE
Re: piCal header
  • 2003/11/13 21:17

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


It's my bug. I'll fix it in piCal 0.507.
If you change externals more radically,
you can use skin feature.

copyall images/default/ to another name
set the directory name into preferences of piCal
change it



166
GIJOE
Re: piCal and birthdays
  • 2003/11/11 7:24

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


hi Jace303.

Quote:

I would also suggest to add the possiblity for configuring the date format for the next version of piCal. Date format in europe differs a little bit from the u.s./japenese format (i.e. "d.m.Y." is most commonly used in german speaking countries).

If you means the format in "event block", I've fixed it in the version >= 0.506.
If not, this is the issue of language files.

You can change the order by editing pical_constants.php
define('_PICAL_FMT_MD','%2$s %1$s') ;
define('_PICAL_FMT_YMD','%3$s %2$s %1$s') ;
define('_PICAL_FMT_YMW','%3$s %2$s %1$s') ;
define('_PICAL_FMT_YEAR_MONTH','%2$s %1$s') ;





167
GIJOE
Re: piCal and birthdays
  • 2003/11/9 22:29

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


hi Jace303.

Though Unix timestamp can't treat date before 1970 well,
your demand is reasonable extremely.

If I can, I want to implement it by adding the extra field of YEAR in the next major version.
This implementation will be limited for schedule view of detail & editing.
The calendar view can still display only between 1970-2037 because of Unix timestamp limitation.




168
GIJOE
Use name() instead of uname()
  • 2003/11/9 12:53

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


Users have two type of name in most systems.
I think that the two names have the following characters each other.

1) Login name
It is used at login.
Therefore, it is necessary to limit the character which can be used.
(Especially with mutlibyte languages)
This information should not be opened to the public too much.
There are some systems which conceals Login name.

2) Nickname ("Real name" in some systems).
It is used for the display.
Because more various expressions are permitted,
the character which can be used should be abundant.

In XOOPS, I believe that uname should be "Login name" and name should be "Nickname".

But almost modules use $xoopsUser->uname() instead of name() for displaying.

"All modules should display Nickname instead of Login name."

If 'name' field isn't suitable for Nickname, 'nickname' field should be added into the user's table by Core Development Team.



169
GIJOE
Re: piCal problem
  • 2003/11/8 8:35

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


hi feral1.

As my translating soft is poor, I can't understand all of what you mean.
I answer in franments.

Quote:

Ideally, I thin, for my site, when entering a calendar event, users should be able to select the correct time-zone at that time. The site should then be able to make adjustments based on the (known) server time zone.
The calendar should then display the event at the correct time for the event, in whichever locality it occurs. As an extra neat feature, it should show the equivalent in universal time (GMT) and in the local time of the viewer.

I think so.
piCal have already prepare to a column for event's timezone.
I'll implement it in next major version.

Quote:

I've had some strange compatibility problems with the module. Notably, if I include a a piCal side panel on the same page as the sections module (main content), the sections page is blank. Once I figured this out, I could remedy the problem easily by not including the piCal side panel on sections pages - but it seems to be a bug...

I have never used the section module.
But piCal is a module with a good manners, I believe.
"Blank page" tells no information to me.
At first, you should turn "PHP debug" on.

_MB_PICAL_JUMP issues has already fixed.
It's a slight mistake.

Quote:

There also seem to be a few issues to resolve with side blocks provided. For instance, I find the MiniCal side panel has some quirks. If there's nothing listed for today, and one clicks on 'Today', it returns to the main Home Page completely outside the calendar. That seems odd. Ideally, I believe, the side block should read either "Today - None" or "Today - View", depending on whether there's content to display.

Today means "jumping to today".
Is it odd?
If you want to display contents on the day, use "Today's block" or "The day's block".



170
GIJOE
Re: photo album question/problem
  • 2003/11/8 8:15

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


If you use myalbum, set these permissions into 777:

module/myalbum/cache
module/myalbum/cache/config.php

But the better way is to use myAlbum-P.
This is a photo album module as "easy to use for begginers".




TopTop
« 1 ... 14 15 16 (17) 18 19 20 21 »



Login

Who's Online

231 user(s) are online (137 user(s) are browsing Support Forums)


Members: 0


Guests: 231


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits