Sponsored Content
The Lounge What is on Your Mind? Prototyping New Responsive Mobile for UNIX.COM - Phase II Post 303006590 by Neo on Saturday 4th of November 2017 01:45:58 AM
Old 11-04-2017
TODO:

- Get avatars and profile images working on the mobile member info page.
- Add links to user posts
- Maybe add Bits?
- Maybe add infraction info?
- Maybe add spam info?

Anything else?
 

8 More Discussions You Might Find Interesting

1. What is on Your Mind?

Mobile App for UNIX.com?

Do we have a mobile app for unix.com? (1 Reply)
Discussion started by: ahamed101
1 Replies

2. Shell Programming and Scripting

Sending message to a mobile number through UNIX

Is it possible to add Pager Notification to mailx command?? Or by any other mean. just want to specify that by Pager i mean a message to the mobile number. Suppose i have following condition If ];then send a message to 9999999999 else no message to be sent fi Is it possible? I... (5 Replies)
Discussion started by: Sharma331
5 Replies

3. What is on Your Mind?

Mobile Friendly Version of UNIX.COM

Hello, I have noticed some problems with Google complaining our site is not "https://search.google.com/www.usearch-console/mobile-friendly" using only Tapatalk. So, after a lot of work, I have re-enabled our legacy mobile style and make some improvements and Google has declared us "mobile... (2 Replies)
Discussion started by: Neo
2 Replies

4. What is on Your Mind?

Prototyping New Responsive Mobile UNIX.COM

I'm working on updates to the mobile phone view, and it's going to look much better I think. Here are some current prototypes: Prototype Mobile Home Page: https://www.unix.com/members/1-albums214-picture690.jpg Prototype Mobile Search Page: ... (43 Replies)
Discussion started by: Neo
43 Replies

5. What is on Your Mind?

Prototyping New Responsive Mobile for UNIX.COM - Phase III

From Prototyping New Responsive Mobile for UNIX.COM - Phase II, we move to Phase III. Basically, the core prototype for every day browsing the forums, replying, posting and editing on mobile is nearly finished with the exception of a few formatting issues with regard to rare system messages or... (4 Replies)
Discussion started by: Neo
4 Replies

6. What is on Your Mind?

New UNIX.COM Mobile Site Icons

Having given up for the time being with a very difficult game engine project to virtualizing cyberspace, am working on the forums again. Just updated a few icons on the mobile site. Explanations in the picture captions: https://www.unix.com/members/1-albums214-picture855.jpeg ... (1 Reply)
Discussion started by: Neo
1 Replies

7. What is on Your Mind?

Check Out UNIX.COM on Mobile - It's Looking Good

If you have not visited the site on mobile lately, you are missing out on a great looking mobile web site. If you don't have a mobile, you can always navigate to the sliding member panel and click on "Mobile View".... It's really looking killer'...... I'm starting to think that soon the... (6 Replies)
Discussion started by: Neo
6 Replies

8. What is on Your Mind?

New Responsive 404 Page for UNIX.com

Just created (actually, only modified... it was created by ShoutOut) a new responsive 404 "not found" page with the help of ShoutOut free templates. https://www.unix.com/status/404.html Same for 401 and 403 errors. Picture sans animation: ... (2 Replies)
Discussion started by: Neo
2 Replies
SYNCE_INFO_NEW(3)					       http://www.synce.org/						 SYNCE_INFO_NEW(3)

NAME
synce_info_new - allocate a new SynceInfo struct SYNOPSIS
#include <synce.h> SynceInfo *synce_info_new(const char *device_name); void synce_info_destroy(SynceInfo *info); const char *synce_info_get_name(SynceInfo *info); bool synce_info_get_os_version(SynceInfo *info, int os_major, int os_minor); int synce_info_get_build_number(SynceInfo *info); int synce_info_get_processor_type(SynceInfo *info); const char *synce_info_get_os_name(SynceInfo *info); const char *synce_info_get_model(SynceInfo *info); const char *synce_info_get_device_ip(SynceInfo *info); const char *synce_info_get_local_ip(SynceInfo *info); int synce_info_get_partner_id_1(SynceInfo *info); int synce_info_get_partner_id_2(SynceInfo *info); const char *synce_info_get_object_path(SynceInfo *info); pid_t synce_info_get_dccm_pid(SynceInfo *info); const char *synce_info_get_transport(SynceInfo *info); const char *synce_info_get_password(SynceInfo *info); int synce_info_get_key(SynceInfo *info); DESCRIPTION
The synce_info_new() function returns a pointer to a newly allocated and populated SynceInfo struct for a mobile device. If device_name is non-NULL, the returned struct relates to a mobile device with that name, or NULL if no device of that name is connected. If device_name is NULL, the exact behaviour depends on the flavour of dccm daemon in use. When using vdccm(1) or the deprecated dccm(1), the current active device is selected. This is usually the last device connected, specifically that described in the active_connection file which is by default in the ~/.synce/ directory. With odccm(1) the first device connected will be returned. With synce-hal this depends on the device(s) in question, and should be considered undefined. This struct should be freed with synce_info_destroy(3). typedef struct _SynceInfo { pid_t dccm_pid; /* process id of dccm daemon */ char* device_ip; /* device ip address */ char* local_iface_ip; /* local interface ip address */ char* password; /* device password */ int key; /* device pass key */ int os_major; /* device OS major version */ int os_minor; /* device OS minor version */ int build_number; /* OS build number */ int processor_type; /* device processor */ int partner_id_1; /* first sync partner id number */ int partner_id_2; /* second sync partner id number */ char* name; /* device name */ char* os_name; /* device OS name eg. PocketPC */ char* model; /* device hardware name */ char* transport; /* interface type */ char* object_path; /* path to device's information */ } SynceInfo; These fields must be accessed with the synce_info_get_ functions. The particular fields populated depend on the flavour of dccm daemon in use. The use of dccm(1) is deprecated. When using vdccm(1) all fields are populated except for local_iface_ip and os_minor. With odccm(1) and synce-hal, dccm_pid, password, key, build_number, partner_id_1 and partner_id_2 are not used. odccm(1) also does not populate local_iface_ip. RETURN VALUE
The synce_info_new() function returns a pointer to the allocated SynceInfo struct, or NULL if an error occured. SEE ALSO
synce(7), odccm(1), vdccm(1) The SynCE Project 2007-08-26 SYNCE_INFO_NEW(3)
All times are GMT -4. The time now is 10:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy