headers
Jeff | 13 Mar 2008 17:22
Picon

Appointment Type dropdown


Is there a reliable way to identify the appointment type dropdown in the Appointment Editor?

I want to just add a real quick check in the LSWAppointmentEditor.js validateEditorContent() routine to throw an error if the selection is = 0 (none).

But the name changes with each load - but is there some way I can build the name of the dropdown in validateEditorContent?

Thanks,
Jeff

Permalink | Reply | 4 comments |
headers
Jeff | 13 Mar 2008 17:34
Picon

Re: Appointment Type dropdown


I think I found a way to do it, but just wanted to check to make sure this would be reliable:

If I get the text at the end of the URL for the form action, and append ".2.1.1.12.1.0.1" to it, that appears to be the appointment type dropdown.

Is that something that could change though?  Or is there a better method than what I'm proposing?

Thanks!
Jeff

On Thu, Mar 13, 2008 at 12:22 PM, Jeff <jhedlund+ogo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Is there a reliable way to identify the appointment type dropdown in the Appointment Editor?

I want to just add a real quick check in the LSWAppointmentEditor.js validateEditorContent() routine to throw an error if the selection is = 0 (none).

But the name changes with each load - but is there some way I can build the name of the dropdown in validateEditorContent?

Thanks,
Jeff


Permalink | Reply | 3 comments |
headers
Helge Hess | 13 Mar 2008 17:41
Favicon

Re: Re: Appointment Type dropdown

On 13.03.2008, at 17:34, Jeff wrote:
> I think I found a way to do it, but just wanted to check to make  
> sure this would be reliable:
>
> If I get the text at the end of the URL for the form action, and  
> append ".2.1.1.12.1.0.1" to it, that appears to be the appointment  
> type dropdown.
>
> Is that something that could change though?  Or is there a better  
> method than what I'm proposing?

No, element-ids are automatically generated and may change. It really  
depends on the form/component, you would usually want to assign a  
static id/value if its not a reusable component.
The WOPopUpButton documentation might help you to get started.

Greets,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/
--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 2 comments |
headers
Jeff | 13 Mar 2008 17:59
Picon

Re: Re: Appointment Type dropdown



On Thu, Mar 13, 2008 at 12:41 PM, Helge Hess <helge.hess-7882/jkIBneb7NEy/Hq5q9i2O/JbrIOy@public.gmane.org> wrote:
No, element-ids are automatically generated and may change. It really
depends on the form/component, you would usually want to assign a
static id/value if its not a reusable component.
The WOPopUpButton documentation might help you to get started.


Thanks - I'll take a look at that.

If I change a wod file, do I have to recompile or just restart ogo?

Thanks,
Jeff
 
Permalink | Reply | 1 comment |
headers
Helge Hess | 13 Mar 2008 18:07
Favicon

Re: Re: Appointment Type dropdown

On 13.03.2008, at 17:59, Jeff wrote:
> If I change a wod file, do I have to recompile or just restart ogo?

Just restart.

Greets,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/
--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 0 comments |
headers
Kit | 20 Mar 2008 13:22
Picon

OGo-1.0 Installation error

I've got:

PPSyncContext.m: In function '-[PPSyncContext
fetchRecordByID:fromDatabase:attributes:category:]':
PPSyncContext.m:974: warning: passing argument 4 of 'dlp_ReadRecordById' from incompatible pointer type
PPSyncContext.m:974: error: too many arguments to function 'dlp_ReadRecordById'
make[3]: *** [shared_debug_obj/PPSyncContext.o] Error 1
make[2]: *** [libPPSync.all.library.variables] Error 2
make[2]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA/PPSync'
make[1]: *** [internal-all] Error 2
make[1]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA'
make: *** [internal-all] Error 2

Anyone can help me ?

System
 cat /etc/issue
Mandriva Linux release 2008.0 (Official) for i586
Kernel 2.6.22.18-desktop-1mdv on an i686 / \l-- 

Thanx
Kit <kit@...>

--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 2 comments |
headers
Helge Hess | 20 Mar 2008 13:55
Favicon

Re: OGo-1.0 Installation error

Hi,

please write to the users <at> ogo mailinglist for installation support.  
You most likely need to deactivate the Palm support, if you don't know  
how, ask on the users list.
Finally, use OGo 1.1.7, not 1.0 which is rather ancient now.

Thanks,
   Helge

On 20.03.2008, at 13:22, Kit wrote:
> I've got:
>
> PPSyncContext.m: In function '-[PPSyncContext
> fetchRecordByID:fromDatabase:attributes:category:]':
> PPSyncContext.m:974: warning: passing argument 4 of  
> 'dlp_ReadRecordById' from incompatible pointer type
> PPSyncContext.m:974: error: too many arguments to function  
> 'dlp_ReadRecordById'
> make[3]: *** [shared_debug_obj/PPSyncContext.o] Error 1
> make[2]: *** [libPPSync.all.library.variables] Error 2
> make[2]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA/ 
> PPSync'
> make[1]: *** [internal-all] Error 2
> make[1]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA'
> make: *** [internal-all] Error 2
>
> Anyone can help me ?
>
> System
> cat /etc/issue
> Mandriva Linux release 2008.0 (Official) for i586
> Kernel 2.6.22.18-desktop-1mdv on an i686 / \l--
>
> Thanx
> Kit <kit@...>

-- 
Helge Hess
http://www.helgehess.eu/
--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 0 comments |
headers
Adam Tauno Williams | 20 Mar 2008 13:58
Favicon

Re: OGo-1.0 Installation error


On Thu, 2008-03-20 at 14:22 +0200, Kit wrote:
> I've got:
> 
> PPSyncContext.m: In function '-[PPSyncContext
> fetchRecordByID:fromDatabase:attributes:category:]':
> PPSyncContext.m:974: warning: passing argument 4 of 'dlp_ReadRecordById' from incompatible pointer type
> PPSyncContext.m:974: error: too many arguments to function 'dlp_ReadRecordById'
> make[3]: *** [shared_debug_obj/PPSyncContext.o] Error 1
> make[2]: *** [libPPSync.all.library.variables] Error 2
> make[2]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA/PPSync'
> make[1]: *** [internal-all] Error 2
> make[1]: Leaving directory `/usr/install/OpenGroupware/OGo-1.0/PDA'
> make: *** [internal-all] Error 2
> Anyone can help me ?

You have an incompatible pilot-link version.  Unfortunately the
pilot-link API changed, and PalmOS 4 vs 5 databases are not compatible,
etc...

I strongly suggest to build with "--without-pisock" which disables the
PDA (Palm OS) module. See -
<http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1638>
<http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1811>
 - if you are interesting in digging into the issue.  

The "--without-pisock" option is mentioned in the installation section
of WMOGAG <http://www.whitemiceconsulting.com/node/67> or
<http://docs.opengroupware.org/Members/whitemice/wmogag/file_view>

My build from source procedure is at
<http://www.whitemiceconsulting.com/node/144>

--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 0 comments |
headers
Helge Hess | 25 Mar 2008 21:44
Favicon

JOPE now Go, on GoogleCode

Hi,

to check out the viability of GoogleCode, I have moved the JOPE  
repository there. In the same run I renamed it to GETobjects, aka Go :-)
(like in O..Go). If it works well, I will also checkin the OGoCore  
Java stuff into GoogleCode. Maybe even SOPE, OGo, SOGo as well. We'll  
see.
All this should take some load from the OGo server machines and  
improve reliability. We even get a Wiki ;-)

Greets,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/
--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 3 comments |
headers
Stéphane Corthésy | 26 Mar 2008 18:18
Picon
Favicon

Bugs in mod_ngobjweb

Hi,

I found bugs in mod_ngobjweb:

In NGBufferedDescriptor.c, at the beginning of  
NGBufferedDescriptor_read(), availBytes is initialized by  
numberOfAvailableReadBufferBytes(self), whereas the test "if(self ==  
NULL)" is done later; this could crash. BTW,  
numberOfAvailableReadBufferBytes(self) should be called only just  
before "if (availBytes >= _len)".

In handler.c:
Around line 721, after NGBufferedDescriptor_safeRead(), you free  
'toApp', but don't NULLify it, and some lines later the pointer is  
freed again when not NULL.
BTW, there is a "#if HEAVY_LOG" whereas everywhere else you use "if 
(HEAVY_LOG)".

I encountered several bugs with this module, when using WOFileUpload.  
I hope these fixes are enough.

Cheers,

Stéphane

--

-- 
OpenGroupware.org Developer
developer@...
http://mail.opengroupware.org/mailman/listinfo/developer
Permalink | Reply | 18 comments |

Gmane